5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

SUBR


The SUBR statement allows you to alter the flow of processing by invoking an APPX subroutine process from within an ILF routine.

  ?????   SUBR     ??? ??????????????????????????????   ??????????   END? ?  FAIL ?
  (1)              (2) (3)                              (4)              (5)     (6)

(1) T/F execution conditions
(2) Application ID
(3) Subroutine process name
(4) Invocation type (SUBPROCESS, RELATED, DETACHED)
(5) End current process first? (Y/N)
(6) Fail action (0=nothing, 1=warning, 2=error, 3=cancel)

Sets True/False Status Indicator

The next status indicator is set to T if the process is invoked successfully, and to F, otherwise. If the process cannot be invoked successfully, the FAIL parameter determines what additional action to take.

Using the Statement

In addition to the application ID and subroutine process name to be invoked, you specify the invocation type (subprocess, related, or detached). As with all other child invocations, this parameter controls the level of data sharing between the parent and the subroutine process invoked.

If END? is set to Y, the current process will end before invoking the subroutine process. The subroutine process will return to the parent of the current process when it is finished. If END? is set to N, the subroutine process returns to the current process (beginning with the first statement after the SUBR statement).

If the application ID is blank, the value in the predefined field NEXT APPLICATION is used. If the process name is blank, the value in the predefined field NEXT PROCESS NAME is used.

Passing Values

The SUBR statement passes the current PASS list, if any. Refer to the PASS Lists section for details.

Related PDF's

NEXT APPLICATION, NEXT PROCESS NAME

Related Statements

COPY, GOSUB, INPUT, INQUIRY, JOB, MENU, OUTPUT, PASS, QUERY, STATUS, UPDATE

Example

The following example checks to see if it is the last processing day in the month. If so, the SUBR statement is executed, invoking an end-of-month calculation routine. 

          IF     TAR WORK END OF MONTH              EQ       Y
  T       SUBR   TAR END OF MONTH CALCULATION             SUBPROCESS   END? Y  FAIL 3

Application Design Manual                                         "Powered by Appx Software"

704

©2006 By APPX Software, Inc. All Rights Reserved